<html>
<head><meta charset="utf-8"><title>Implementation strategy for try_trait_v2 [libs-impl] · t-libs · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/index.html">t-libs</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/Implementation.20strategy.20for.20try_trait_v2.20.5Blibs-impl.5D.html">Implementation strategy for try_trait_v2 [libs-impl]</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="233997729"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/Implementation%20strategy%20for%20try_trait_v2%20%5Blibs-impl%5D/near/233997729" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> scottmcm <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/Implementation.20strategy.20for.20try_trait_v2.20.5Blibs-impl.5D.html#233997729">(Apr 10 2021 at 23:24)</a>:</h4>
<p>Assuming the FCP goes well, any thoughts on how the transition on nightly should go?  With bootstrapping it'll be somewhat exciting, especially with the associated type name change.</p>
<p>I was pondering something like:</p>
<ul>
<li>PR to add the new trait and implementations, via an unstable <code>pub use try_trait::Try as TryV2;</code> so it doesn't break the other things.</li>
<li>PR to move all the <code>Try&lt;Ok = T&gt;</code> bounds to an unstable trait alias</li>
<li>PR to actually implement the desugaring and start <code>cfg(bootstrap)</code>ing things.</li>
<li>PR to remove all the transitional stuff after the new lang items and such are in the bootstrap beta version.</li>
</ul>
<p>Thoughts?</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>